Release 10.1A: OpenEdge Data Management:
DataServer for ORACLE

Connecting a schema holder at startup

OpenEdge supports connection parameters that you can use to connect the OpenEdge schema holder and the ORACLE database. These parameters control how your system connects to a database. When the OpenEdge DataServer for ORACLE runs in a remote configuration, your startup command or parameter file must include parameters that control networking options.

Table 6–2 describes the connection parameters that relate to the remote DataServer and networking options.

Table 6–2: Remote DataServer connection parameters 

Parameter	Description
Host Name (-H)	Indicates the name of the host machine in the network.
Service Name (-S)	Indicates the name of the service you are calling. The service you are calling is the broker on the host machine. Use the same name you used when you started the broker.

The following command starts OpenEdge for Windows:

prowin32 schemaholdername -db fill-char -dt ORACLE -ld oracle-logical-db-name -H hostname -S service-name -U userID -P password

You can use the previous command to start OpenEdge for Windows in the following situations:

In single-user mode.
In a remote-DataServer configuration.
With a local schema holder connected.
With an ORACLE database connected.

Table 6–3 describes the parameters required for connecting to a schema holder and an ORACLE database.

Table 6–3: Required connection parameters 

Parameter	Description
User ID (-U)	Supplies the user ID that the OpenEdge DataServer for ORACLE uses to log into the ORACLE RDBMS. ORACLE allows you to pass the user ID and password as a single string to the -U parameter. If you specify -U userid/password or -U userid/password@service-name, the USERID function returns the password information or the password and service in addition to the user ID.
Password (-P)	Supplies the password that the OpenEdge DataServer for ORACLE uses to log into the ORACLE RDBMS unless it was specified with the -U parameter.
Physical Database Name (-db)	For OpenEdge databases, the string that follows this parameter is the physical name of the database you want to connect. However, for ORACLE databases, this physical database name can be any fill characters. For example, use the logical database name after the -db parameter or any other designation, such as oradb.
Single-user Mode (-1) or Read-only (-RO)	Specifies that a database is used in single-user mode. When you connect the schema holder, you must connect either in single-user mode or as read-only. Specifies that a schema holder is read-only. Connecting a schema holder as read-only increases processing speed at compile time. It also allows multiple client processes on the same machine to access the schema holder without starting additional server processes.

You can create a parameter file with the required parameters for each database. You can add more startup parameters than the ones listed—these are just the required parameters. For information on how to create a parameter file, see OpenEdge Deployment: Startup Command and Parameter Reference .

The following example commands demonstrate how to start DataServer clients that connect to the schema holder and ORACLE database at startup.

Remote DataServer — Windows client

In this example, the schema holder’s physical name is oholder; it is read-only; the ORACLE database’s logical name is orademo; the host name is host1; the service name is oserviceA; the user ID is scott; the password is tiger. This configuration assumes you started the remote DataServer broker using the command line interface:

prowin32 oholder -RO -db oradb -ld orademo -H host1 -S oserviceA -U scott -P tiger

Remote DataServer via NameServer — Windows client

The following attributes pertain to the code presented in the example presented in this section:

The schema holder’s physical name is oholder and it is read-only.
The ORACLE database’s logical name is orademo.
The user ID is scott.
The password is tiger.
The host where the NameServer is running is nshost.
The service is port number 5162, the default port of the Name Server.
The -Dsrv switch indicates this connection is using a NameServer.
The DataService is orabroker1.

prowin32 oholder -RO -db oradb -ld orademo -U scott -P tiger -H nshost -S 5162 -Dsrv SVUB,1 -DataService orabroker1

Local DataServer — Windows

In this example, the schema holder’s physical name is oholder; it is read-only; the ORACLE database’s logical name is orademo; the user ID is scott; and the password is tiger:

prowin32 oholder -RO -db oradb -ld orademo -U scott -P tiger

The DataServer is local so there is no need for host and service parameters.

Remote DataServer — UNIX Client

In this example, the schema holder’s physical name is oholder; it is read-only; the ORACLE database’s logical name is orademo; the remote DataServer host is host1; the service name for the DataServer broker is oserviceA; the user ID is scott; and the password is tiger. This configuration assumes you started the remote DataServer broker using the command line interface, as shown:

pro oholder -RO -db oradb -ld orademo -H host1 -S oserviceA -U scott -P tiger

Local DataServer — UNIX

In this example, the schema holder’s physical name is oholder; it is read-only; the ORACLE database’s logical name is orademo; the user ID is scott; and the password is tiger:

pro oholder -RO -db oradb -ld orademo -U scott -P tiger

The DataServer is local, so there is no need for host and service parameters.